home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
spitfire
/
sfemb051.zip
/
SFEMB.DOC
< prev
next >
Wrap
Text File
|
1996-03-19
|
16KB
|
376 lines
SF Enhanced Message Base
(Pre 1.0 Version)
January 31, 1995
Written By David D. Turley
"Spitfire can now have a full screen editor? Right..."
SF Enhanced Message Base (SFEMB) is a great way to enhance
your SPITFIRE BBS system! With the now common 14.4 bps
modems, the old "line by line" editor and reader that you
normally use could really use a bit of pizazz. SFEMB gives
you that pizazz and more! With full screen controls,
editing, and indexes, you'll find your message base open up
to new possibilities! Personal BIO's, Alias posting,
Enhanced message scanning, Internal DOOR loading, Global
messages, Editing users right in the message base! All this
and more!
You'll agree, this is quite a program! Give it a try and
see what you think!
** BETA RELEASE ** This program is in beta form. Steps are
taken to preserve data integrity, however some bugs
unfortunately will be passed on to you, the sysop. Be
advised the author takes no responsibility for damage done
software or hardware as a result of this program. Use at
your own risk.
USAGE:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
To upgrade from a previous version of SFEMB, you need to update
this copy of SFEMB (if shareware). To do this, place your old
copy of SFEMB in a safe directory. Execute your NEW copy of SFEMB
with the word "REGISTER" after it:
C:\SF>SFEMB REGISTER
You will be asked for the directory you placed your old copy of
SFEMB in. Once the new copy of SFEMB confirms the previous
registration, it will register itself. If you have any problems,
please contact the support BBS.
SFEMB is designed to be operated as a DOOR, or from the
command line. It gives the sysop and user greater freedom
with the message base than they've had in the past.
FORMAT:
C:\SF> SFEMB.EXE [<drive:path>bbsfile.ext [SCAN [FORCE]]]
WHERE:
<drive:path> The full path location of the bbsfile.
(optional)
bbsfile.ext The name of the drop file. (eg.
SFDOORS.DAT, SFMAIN.DAT, SFMESS.DAT,
SFFILE.DAT) (required for DOOR
operation, option for command line
"local" initiation).
SCAN Puts SFEMB into "SCAN" mode. This is
used in a SFLOGON.BAT or similar file.
This can only be executed during a DOOR
initiation.
FORCE A special "SCAN" mode modifier, it
disallows user from aborting a message
scan part-way.
USAGE EXAMPLES:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
SFLOGON.BAT Example -
SFEMB.EXE C:\SF\SFDOORS.DAT SCAN FORCE
The above example would load SFEMB and put it into a "Forced
Scan" mode. SFEMB will scan all messages in all conferences
looking for new messages to the logged on user. If message
are found, the user can enter the reader/editor and read the
new messages.
SF.BAT DOOR Example -
DOOR_M
SFEMB.EXE C:\SF\SFDOORS.DAT
GOTO LOOP
SFMAIN.BAT MENU EXTENSION Example -
SFEMB.EXE C:\SF\SFMAIN.DAT
DOS Command line initiation example -
SFEMB.EXE
The above examples will load the main SFEMB program. SFEMB
will load with all features being active.
EMB.BAT:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
SFEMB is a large program. In order to gain the maximum
amount of memory for execution of external DOORS, it was
necessary for SFEMB to completely unload from memory in
order to execute an external DOOR. For proper execution of
external DOORS within SFEMB, you will need to use the
EMB.BAT (or similar) file. When an external door is
selected for loading, SFEMB creates a "state of affairs"
file called EMBSYS.<node#>. It then exits with an error
code notifying the EMB.BAT which door to load. When the
external door is finished, SFEMB re-loads and is ready right
where you left off.
SFEMB is capable of operating up to 15 external DOORS.
SF Sysops are already familiar with this type of external
DOOR loading, and editing and maintain this file will not be
a hassle. We give you the EMB.BAT file as an example to be
modified or copied to further understand DOOR loading.
SFEMB.CFG:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
This file is the heart of SFEMB. If something is not
working right, then a good chance is that this file is to
blame.
** NOTE ** SFEMB looks for the SFEMB.CFG in the current
directory. If your BBS needs unique SFEMB.CFG files for
each of its nodes, you are advised to put the .CFG files in
different directories and start SFEMB from the respective
directories.
EXAMPLE:
C:\SF\NODE1\SFEMB.CFG
C:\SF\NODE2\SFEMB.CFG
or
X:\DOORS\SFEMB\NODE1\SFEMB.CFG
X:\DOORS\SFEMB\NODE4\SFEMB.CFG
FORMAT:
-------
SFEMB is controlled by several command variables within the
SFEMB.CFG file. The format of the .CFG file is as follows:
FORMAT:
<variable>=<argument>;
WHERE:
<variable> A valid command-variable name. Note
that no spaces may separate the variable
and the "=" and the "=" and the
argument. Generally not case sensitive.
<argument> The value given to the variable. Can be
case sensitive.
Anywhere in the .CFG file a ";" can be used to denote a
comment. Lines beginning with a ";" are considered to be
comments.
VARIABLES:
----------
The following is a list and explanation of all the valid
command-variables.
allow.alias Turns on and off the ALIAS features of
SFEMB. [Default=TRUE]
allow.quotebox Turns on and off the QuoteBOX feature of
SFEMB. QuoteBOX is an alternate method
of quoting a user with the old "DT> "
method. QuoteBOX is a High-ASCII box
that is placed around the quote to give
it a more asthetic look. [DEFAULT=TRUE]
bbs.citystate Places a line at the end of your messages
giving the city/state/country or whatever
you wish. This will be printed on the next
line below the TCode.
beta.bbsname Tells SFEMB the name of YOUR BBS on a
timed beta release. After the beta
period has elapsed for a given beta, the
variable will be ignored and SFEMB will
report the program as unregistered.
color.<type> This is a series of variables allowing
the sysop to customize the color set
used by SFEMB. Please look at the
supplied SFEMB.CFG for further
information.
common.directory Where SFEMB expects to find its .HLP
files. It also stores its USERS.EMB
file, and the BIO sub-directory there.
All nodes in a multi-node BBS should
have the *SAME* common.directory.
[Default=C:\SF\WORK]
default.bbspath Where SFEMB looks to find the
SFMCONF.DAT & SFNODE.DAT during command
line initiation. [Default=C:\SF]
default.name What name SFEMB assumes the active user
to be when it is loaded from the command
line without a BBS drop file.
[Default=Sysop]
default.security Security level of the active user during
command line initiation. [Default=999]
default.usernumber The default user number to assume during
command line initiation. Used to load
the correct Last Message Read pointers.
[Default=0]
door_<ltr>.<ecode> This is a series of variables used to
activate the external DOOR features of
SFEMB. The <ltr> corresponds to the
letter that option will appear in the
menu as. The <ecode> is the error code
the program will result if that option
is selected. Non-used
door_<ltr>.<ecode> variables should be
commented out by using a leading ";".
ignore.fossil Tells SFEMB to ignore any FOSSIL drivers
even if it finds some present.
[Default=FALSE]
local.ripview Points to a .BAT file that will be
loaded when a local user wishes to
<V>iew a message through a RIP (or ANSI)
interpreter. A copy of the message is
passed to the .BAT file as the first
parameter to it.
message.directory Where SFEMB expects to find all the
messages. All nodes in a multi-node BBS
should have the *SAME*
message.directory.
[Default=C:\SF\MESSAGE]
overide.bbspath Overrides the bbs_path supplied by the
BBS drop-file. This may be used to let
SFEMB access multiple message bases.
scan.queue.only This variable turns on and off the usage
of the message Queue during SCAN mode.
If on, any SCAN will only scan the users
queued conferences instead of all
conferences.
showlast.msg In the main menu of SFEMB, it displays
the last few message headers (#, to,
from, & subject) in a given conference.
This tells SFEMB how many to display.
Too many displayed may cause the screen
to scroll unnecessarily.
sysop.security Level user must obtain to have full
sysop privileges within SFEMB.
*WARNING* Users with sysop status have
full access to the user password file.
[Default=999]
turley.code This variable sets your BBS's TurleyCode
so that other users who read messages
from your BBS will know what kind of BBS
you operate. (See BBSCODE.TXT for more
information)
use.circuitnet This instructs SFEMB to look for and use
CircuitNET Software routing codes.
[Default=FALSE]
work.directory This is where SFEMB puts its temporary
work files. This can be a RAM disk, and
might be preferred in order to minimize
disk clutter. [Default=C:\SF]
HELP FILES:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Help files should all be located in the "common.directory". If
not, an error message will be displayed to the user when they
attempt to access the help screens.
NET.ID:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
SFEMB now adds to the normal information in the conference
header by adding a NetID byte. This gives each conference a
number that identifies it to a specific conference. This
number can be any number 0 through 255. The number can be
associated with a name via the NET.ID file. This is a simple
text file located in the same directory the MESSAGE base is
located in. (NOT the SFMCONF.DAT file) The file format is
simple:
<NetID>,<Name>
Example:
0,Local
1,FIDONet
2,BingoNet
10,SFNET
11,CNFDNet
The NetID number also has meaning. Numbers 0 & 10-255 are
considered "Normal" networks. Conference numbers 1-9 are
considered to be "LOW ASCII" conferences, and the QuoteBOX
is not allowed in these conferences.
EMB_ERR.LOG:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
SFEMB creates an EMB_ERR.LOG file and stores in it all of
the exit code information. This is used in the beta-testing
procedure to track errors on certain versions. This file
will need to be periodically deleted. When SFEMB comes to a
non-progressable error, it will gracefully (hopefully)
terminate and give store the relevant information in the
EMB_ERR.LOG. This information can be forwarded to the
support BBS for further analysis and problem solving.
REGISTRATION:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
There is no time limit to register the software. You may
use the unregistered version forever. You are encouraged to
register this program if you feel it adds to the value of
your BBS. Many shareware authors charge more for their
programs, but I felt that the low price of $10 would be
adequate. The unregistered version is not crippled in any
way. Registration gives you free upgrades to all future
versions.
Registration is easy, just send $10 (check or money order,
[or cash if you feel lucky] paid to the order of David D.
Turley) along with the registration form to the name and
address below. People receiving disks will also receive a
copy of all the shareware written by David D. Turley to
date. Print the file REGISTER.FRM, fill it out, and send it
to the following:
Send to: David D. Turley
4491 West 3500 South C-2
West Valley City, Utah 84120-3069
*NOTE* Mail sent to the above address is forwarded to the
authors actual address (I move frequently). This may
account for why it may take longer than typical mail time to
get here. Registrations are generally done twice monthly,
however we often get bored and just catch ourselves up with
everything in to date. If you are requesting an "uploaded"
registration, please notate on the registration form when a
good time of day would be to call your BBS and get on
without waiting through hours of busy signals.
COMMENTS:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Any comments or questions concerning SFEMB, or other
programs written by the author can be sent to the above
address. You may reach us on-line, or obtain an instant
upgrade of any software you have registered from us through
our Support BBS:
Sanctuary BBS
(801) 968-3631,
24 hours, v.32/42bis.
Donations of your older hardware (which would improve the
performance of Sanctuary BBS) may be negotiated with the
author to obtain free registration of this and other
software written by the author. Please inquire with the
author, David D. Turley for more information.
DISCLAIMER:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Use SFEMB at your own risk. The author of SFEMB takes no
responsibility for damage caused to your hardware or
software, caused in anyway by SFEMB or its related files.
Always check new software with virus checkers before using
them.
All software mentioned in this document are copyrighted to
their respective owners.